Embed Visier in Your Application

Embed Visier's analytic solution into your product.

Note: Before embedding Visier in your application, review Visier's Supported Browsers and System Requirements.

You can embed Visier into your product in these ways:

  • Full embedding: Users can open the entire Visier application from your application on the same page or in a new tab while keeping the same session. This option gives you the flexibility to build a custom navigation experience or use Visier's default navigation. In the following screenshot, a user can click Analytics on your navigation bar to open Visier, which has another navigation bar for navigating the Visier application.

  • Distributed access: You can embed multiple Visier rooms in your navigation bar rather than embedding the entire Visier application in one room. In the following screenshot, a user can click Executive Insights on your navigation bar to open a Visier analysis. The Visier analysis does not have a navigation bar because it is one analysis, not the full Visier application.

  • In-flow: Users can view visualizations directly in the context of their work in your application. In-flow visualizations are not interactive, but you can optionally redirect users to an interactive application if they click on the embedded visualization. In the following screenshot, a user is navigating one of your application pages and can see Visier content embedded directly on the page, such as Time to Fill metrics and visualizations.

  • Tab out: Rather than embed Visier directly in your application, you can allow users to open Visier in a new tab. In the following screenshot, a user opened Visier from your application into a new tab.

We can compare the benefits and drawbacks of each integration approach.

Full embedding

Pros:

  • Provides the complete Visier analytics experience.
  • Requires minimal user interface implementation work; Visier provides code snippet examples.
  • Provides flexibility to build your own navigation menu or use our default.

Cons:

  • Provides limited user interface input options that are limited to the preset navigation menu.
Distributed access
Pros:
  • Allows full control of the navigation and analytic experience.
  • Enables you to embed a set of tailored analysis to solve specific business questions.
  • Leverages Visier's pre-built controls (filters, group bys, Detailed View, and more) to avoid extensive user interface development.

Cons:

  • Provides limited control over the look and feel of analyses.
  • Causes performance impact if session management is not handled properly with the hidden iframe.
In-flow
Pros:
  • Provides flexibility to control visuals in the flow of work.
  • Empowers decision-making for end users by bringing analytics to where their work happens.
  • Adds value for the organization by making it easy for the user to make data-driven decisions.
  • Increases adoption and engagement with analytics by providing a gateway to analytics.
  • Makes analytics more "sticky" by making it an essential part of user workflows.

Cons:

  • Requires upfront effort to design workflows and user interfaces.
  • Requires additional development efforts.
Tab out

Pros:

  • Requires the least amount of development effort.
  • Provides the complete Visier analytics experience.

Cons:

  • Provides a more decoupled experience between your application and Visier's analytic solution.
  • Prevents full application white labeling because the new tab's URL is your Visier URL; for example, jupiter.visier.com.

Note: Not recommended unless time-to-market is the highest priority and development time is a minimum.

For more information, see Visier Embedded Docs.